Determine whether to rebuild track metadata to determine whether a track format table has a track format code for the track format metadata

ABSTRACT

Provided are a computer program product, system, and method for managing read and write requests from a host to tracks in storage cached in a cache. A determination is made whether track format table support information for a track indicates that a track format table was previously determined to have or not have the track format code for track format metadata. Track format metadata for the track is rebuilt to determine whether the track format table includes a track format code for the rebuilt track format metadata when the track format table support information indicates that the track format table was previously determined to have a track format code for the track. The track format metadata is not rebuilt when the track format table support information indicates that the track format table was previously determined to not have a track format code for the track.

BACKGROUND OF THE INVENTION 1. Field of the Invention

The present invention relates to a computer program product, system, and method to determine whether to rebuild track metadata to determine whether a track format table has a track format code for the track format metadata.

2. Description of the Related Art

In a storage environment, a host system may communicate a read/write request to a connected storage system over network channel through a network adaptor. If the data is in a cache of the storage system, i.e., a read hit, then the data may be returned quickly to the host system. This reduces the delay in returning requested data to a host I/O request. However, if the requested data is not in the cache of the storage system, then there may be significant latency realized while the storage system needs to retrieve the requested data from storage to return. Further, the thread or task executing the host read request may have to be context switched and deactivated in order to allow the host system to process further I/O requests. When the data is returned to the read request, then the task must be reactivated and data for the task must be returned to registers and processor cache to allow processing of the returned data for the read request.

There is a need in the art for improved techniques for processing host read/write requests to the cache.

SUMMARY

Provided are a computer program product, system, and method for managing read and write requests from a host to tracks in storage cached in a cache. A determination is made whether track format table support information for a track indicates that a track format table was previously determined to have a track format code for track format metadata for the track or was determined to not have the track format code for the track format metadata. Track format metadata for the track is rebuilt to determine whether the track format table includes a track format code for the rebuilt track format metadata in response to determining that the track format table support information indicates that the track format table was previously determined to have a track format code for the track. The track format metadata is not rebuilt to determine whether the track format table has a track format code for the track format metadata in response to determining that the track format table support information indicates that the track format table was previously determined to not have a track format code for the track.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an embodiment of a storage environment.

FIG. 2 illustrates an embodiment of a track format table entry.

FIG. 3 illustrates an embodiment of a cache control block.

FIG. 4 illustrates an embodiment of a Least Recently Used (LRU) list of tracks in the cache.

FIG. 5 illustrates an embodiment of operations to process a read/write request received on a first channel, such as a bus interface.

FIG. 6 illustrates receive an embodiment of operations to process a read/write request received on a second channel, such as a network.

FIG. 7 illustrates an embodiment of operations to close track metadata and determine a track format code for the track in cache of the closed track metadata.

FIG. 8 illustrates an embodiment of operations to invalidate a metadata track.

FIG. 9 illustrates an embodiment of a storage environment having multiple processing nodes.

FIG. 10 illustrates an embodiment of operations to failover from one processing node in the storage system to another processing node.

FIG. 11 illustrates an embodiment of operations to determine whether to rebuild track format metadata and determine a track format code for the track format metadata.

FIG. 12 illustrates an embodiment of a computer architecture used with described embodiments.

DETAILED DESCRIPTION

In a storage environment, a host system may first communicate a read/write request to a connected storage system over a fast channel, such as a bus interface, such as the Peripheral Component Interconnect Express (PCIe) interface. For a read/write request over the fast channel which is supposed to complete within a threshold time, the host system holds the application thread for the read/write request in a spin loop waiting for the request to complete. This saves processor time associated with a context swap, which deactivates the thread and reactivates the thread in response to an interrupt when a response to the read/write request is received. If the data for the read/write request sent on the fast channel is not in cache, then the storage system may fail the read/write request and the host system may communicate the same read/write request over a storage area network via a host adaptor, which is slower than processing the I/O request over the bus, e.g., PCIe interface. Communicating the read/write request over the second channel requires the host system to perform a context switch from the task handling the read/write request to another task while waiting for the read/write request to complete. Context switching is costly because it requires the processor running the task to clear all registers and L1 and L2 caches for the new task, and then when completing the new task, reactivate the context switched task and return the state data to the registers and L1 and L2 caches for the task that was context switched while waiting for the read/write request to complete.

Certain read/write operations need to be completed within a threshold time, else they are failed. The storage system will have to access track metadata to process a request to a track. The track metadata provides information on the format of data and layout of records in the track that are needed in order to perform reads and writes to the track. However, the reading of the track metadata from the storage comprises a substantial portion of the latency in processing read/write request. Described embodiments provide improvements to cache technology that reduce cache operation latency by including a track format code in the cache control block for a track in the cache. This track format code may be used for fast access to the track format from a track format table without having to read the track metadata from storage. By eliminating the need to read the track metadata from a metadata track in storage to determine the track layout, described embodiments increase the likelihood that read/write requests on the first channel that need to be completed within a threshold time are completed by accessing the track layout information for a track from the track format table, associating track format codes with track format information for common track formats.

With described embodiments, a read/write request to a target track on a channel requiring that the request be completed within a threshold time is processed if the track format code for the target track is within the cache control block for the target track. Using the track format code to access the track format metadata from the track format table reduces the latency of access to the track format metadata to allow the read/write request to complete within the time threshold. This keeps the time the host thread is spinning on the read/write request task for the read/write request sent on the bus interface within an acceptable time threshold. However, if the cache control block for the target track does not have a valid track format code, then the read/write request on the first channel is failed because it is unlikely the read/write request can complete within the threshold time given that the track format metadata will have to be retrieved from the storage. Failing the read/write request on the first channel, causes the host to redrive the read/write request on the second channel. The processing of the read/write request on the second channel reads in the track metadata from the storage to allow for processing the read/write request and adding the track format code to the cache control block for the target track.

Further, described embodiments provide track format table support information on the results of a prior determination of whether the track format table provided a track format code for the track format metadata, such as indication that there was or was not a track format code in the track format table for the track format metadata, or that the track format code was invalidated without making a determination whether the track format table included a code for the track format metadata. This support information may then later be used to determine whether to expend processing resources to rebuild track metadata to determine whether the track format table provides a track format code when the track format code is currently invalid. This support information optimizes the process by only rebuilding the track metadata to make this determination if there is a likelihood the track format table does provide a track format code for the track format metadata, such as if a track format code was previously determined for the track format metadata or the track format metadata was invalidated without determining whether the track format table provided a track format code for the track format metadata. However, if the support information indicates that the track format table is unlikely to provide a track format code for the track format metadata, such as if the support information indicates that in a previous determination the track format table did not provide a track format code for the track format metadata, then the track metadata will not be rebuilt because it is unlikely, given the previous determination, that a track format code will be found in the track format table. In this way, processor resources are optimized by using the track format table support information to determine when the track format metadata will be rebuilt to determine if there is a track format code in the track format table.

FIG. 1 illustrates an embodiment of a storage environment in which a host 100 directs read and write requests to a storage system 102 to access tracks in volumes configured in storage devices 104 in a disk enclosure 106. The host 100 includes a processor complex 108 of one or more processor devices and a memory 110 including an operating system 111 executed by the processor complex 108. The host operating system 111 generates read and write requests to tracks configured in the storage devices 104. The host 100 includes hardware to communicate read and write requests on two different channels. A first channel is a bus interface, such as a Peripheral Component Interconnect Express (PCIe), including a bus 112, a bus switch 114 to connect one or more devices on the bus 112, including the processor complex 108, a memory system 110, and a bus host adaptor 116 to extend the bus interface over an external bus interface cable 118 to the storage system 102. Additional bus interface technology to extend the bus interface may be utilized, including PCIe extender cables or components, such as a distributed PCIe switch, to allow PCIe over Ethernet, such as with the ExpEther technology. A second channel to connect the host 100 and storage system 102 uses a network host adaptor 120, connected to the bus 112, that connects to a separate network 122 over which the host 100 and storage system 102 additionally communicate. The first channel through the bus interface may comprise a faster access channel than the network 122 interface through the network host adaptor 120.

The storage system 102 includes a bus interface comprising a bus 124 a, 124 b, a bus switch 126 to connect to endpoint devices on the bus 124 a, 124 b, and a bus host adaptor 128 to connect to the external bus interface cable 118 to allow communication over the bus interface to the host 100 over the first channel. The storage system 102 includes an Input/Output bay 130 having the bus host adaptor 128, one or more device adaptors 132 to connect to the storage devices 104, and one or more network host adaptors 134 to connect to the network 122 and host systems.

The storage system 102 includes a processor complex 136 of one or more processor devices and a memory 138 having a cache 140 to cache tracks accessed by the connected hosts 100. The memory 138 includes a cache manager 142 and a storage manager 144. The storage manager 144 manages access requests from processes in the hosts 100 and storage system 102 for tracks in the storage 104. The devices 136, 138, 128, 132, and 134 connect over the bus interface implemented in the bus lanes 124 a, 124 b and bus switch 126.

The cache manager 142 maintains accessed tracks in the cache 140 for future read access to the tracks to allow the accessed tracks to be returned from the faster access cache 140 instead of having to retrieve from the storage 104. Further, tracks in the cache 140 may be updated by writes. A track may comprise any unit of data configured in the storage 104, such as a track, Logical Block Address (LBA), etc., which is part of a larger grouping of tracks, such as a volume, logical device, etc.

The cache manager 142 maintains cache management information 146 in the memory 138 to manage read (unmodified) and write (modified) tracks in the cache 140. The cache management information 146 may include a track format table 200 having track format codes for common track format descriptors providing details of a layout and format of data in a track; track index 148 providing an index of tracks in the cache 140 to cache control blocks in a control block directory 300; and a Least Recently Used (LRU) list 400 for tracks in the cache 140. The control block directory 300 includes the cache control blocks, where there is one cache control block for each track in the cache 140 providing metadata on the track in the cache 140. The track index 148 associates tracks with the cache control blocks providing information on the tracks in the cache 140. Upon determining that the cache LRU list 400 is full or has reached a threshold level, tracks are demoted from the LRU list 400 to make room for more tracks to stage into the cache 140 from the storage 104.

In certain embodiments, there may be multiple hosts 100 that connect to the storage system 102 over the first and second channels to access tracks in the storage devices 104. In such case, the storage system 102 would have at least one bus host adaptor 128 to connect to the bus interface 118 of each connected host 100 and one or more network host adaptors 134 to connect to the network host adaptors 120 on the hosts 100.

In one embodiment, the bus interfaces 112, 114, 116, 118, 124 a, 124 b, 126, and 128 may comprise a Peripheral Component Interconnect Express (PCIe) bus interface technology. In alternative embodiments, the bus interfaces 112, 114, 116, 118, 124 a, 124 b, 126, and 128 may utilize suitable bus interface technology other than PCIe. The bus host adaptors 116 and 128 may comprise PCIe host adaptors that provide the interface to connect to the PCIe cable 118. The network 122 may comprise a Storage Area Network (SAN), a Local Area Network (LAN), a Wide Area Network (WAN), the Internet, an Intranet, etc., and the network host adaptors 120, 134 provide the network 122 connections between the hosts 100 and storage system 102.

The storage system 102 may comprise a storage system, such as the International Business Machines Corporation (IBM®) DS8000® and DS8880 storage systems, or storage controllers and storage systems from other vendors. (IBM and DS8000 are trademarks of International Business Machines Corporation throughout the world). The host operating system 111 may comprise an operating system such as Z Systems Operating System (Z/OS®) from International Business Machines Corporation (“IBM”) or other operating systems known in the art. (Z/OS is a registered trademark of IBM throughout the world).

The storage devices 104 in the disk enclosure 106 may comprise different types or classes of storage devices, such as magnetic hard disk drives, solid state storage device (SSD) comprised of solid state electronics, EEPROM (Electrically Erasable Programmable Read-Only Memory), flash memory, flash disk, Random Access Memory (RAM) drive, storage-class memory (SCM), etc., Phase Change Memory (PCM), resistive random access memory (RRAM), spin transfer torque memory (STT-RAM), conductive bridging RAM (CBRAM), magnetic hard disk drive, optical disk, tape, etc. Volumes in a storage space may further be configured from an array of devices, such as Just a Bunch of Disks (JBOD), Direct Access Storage Device (DASD), Redundant Array of Independent Disks (RAID) array, virtualization device, etc. Further, the storage devices 104 in the disk enclosure 106 may comprise heterogeneous storage devices from different vendors and different types of storage devices, such as a first type of storage devices, e.g., hard disk drives, that have a slower data transfer rate than a second type of storage devices, e.g., SSDs.

FIG. 2 illustrates an embodiment of a track format table entry 200 _(i) in the track format table 200, which includes a track format code 202 and the track format metadata 204. In certain embodiments Count Key Data (CKD) track embodiments, the track format metadata 204 may comprise a track format descriptor (TFD) indicating a number of records in the track, a block size, a number of blocks in the track, a data length of each of the records, and a control interval size indicating an amount of data that is read or written atomically as a unit, number of blocks in a control interval, and whether a control interval spans two tracks, and other information. The track format code 202 may comprise an index value of the index entry 200 _(i) in the track format table 200. For instance, if there are 32 track format table entries 200 _(i), then the track format code 202 may comprise 5 bits to reference the different possible number of 32 entries 200 _(i).

FIG. 3 illustrates an embodiment of a cache control block 300 _(i) for one of the tracks in the cache 140, including, but not limited to, a cache control block identifier 302, such as an index value of the cache control block 300 _(i); a track ID 304 of the track in the storage 104; the cache LRU list 306 in which the cache control block 300 _(i) is indicated; an LRU list entry 308 at which the track is indicated; a cache timestamp 310 indicating a time the track was added to the cache 140 and indicated on the LRU list 306; additional track metadata 312 typically maintained for tracks stored in the cache 140, such as a dirty flag indicting whether the track was modified; a track format code 314 comprising one of the track format codes 202 of the track format metadata 204 describing the layout of data in the track 304 represented by the cache control block 300 _(i); a track format code valid flag 316 indicating whether the track format code 314 is valid or invalid; and track format table support information 318 indicating whether the track format table 200 previously provided a track format code for the track or a reason why the track format code was invalidated, such as due to a determination the track format table 200 did not provide a track format code 202 for the track format metadata, or that the track format code was invalidated without determining whether the track format table 200 provided a track format code 202 for the track format metadata.

FIG. 4 illustrates an embodiment of an LRU list 400 _(i), such as having a most recently used (MRU) end 402 identifying a track most recently added to the cache 140 or most recently accessed in the cache 140 and a least recently used (LRU) end 404 from which the track identified at the LRU end 404 is selected to demote from the cache 140. The MRU end 402 and LRU end 404 point to track identifiers, such as a track identifier address or a cache control block index for the track, of the tracks that have been most recently added and in the cache 140 the longest, respectively, for tracks indicated in that list 400.

FIG. 5 illustrates an embodiment of operations performed by the cache manager 142 and storage manager 144 to process a read/write request to a target track received on a first fast channel, such as the PCIe bus interface via bus host adaptor 128. Upon receiving (at block 500) the read/write request at the bus host adaptor 128, if (at block 502) the target track is not in the cache 140, then the storage manager 144 returns (at block 504) fail to the read/write request on the first channel or bus host adaptor 128 to the host 100, which causes the host 100 to retry the read/write request on the second channel or network host adaptor 120, 134. Failure is returned because if the target track is not in the cache 140, then the target track and track metadata needs to be staged into cache 140, which would likely exceed the time threshold for read/writes on the first channel, where the host processor is spinning on the thread of the read/write request. If (at block 502) the target track is in the cache 140 is a write and if (at block 508) the write modifies the track format, then the cache manager 142 sets (at block 510) the track format code valid flag 316 to invalid. The cache manager 142 indicates (at block 512) in the track format table support information 318 that no determination was made whether the track format table 200 supports the new track format metadata resulting from the write to the track modifying the track format. The storage manager 144 then returns (at block 504) fail to the host 100 because the track metadata needs to be read from the storage 104 to update with the modified track format.

If (at block 506) the read/write request is a read or if (at block 508) the request is a write that does not modify the track format, then the cache manager 142 determines (at block 514) if the track format code valid flag 316 is set to valid. If so, then the cache manager 142 determines (at block 516) the track format metadata 204 in the track format table 200 corresponding to the track format code 314 in the cache control block 300 _(i). The cache manager 142 uses (at block 518) the track format layout indicated in the determined track format metadata 204 to process the read or write request to the target track in the cache 140. If the request is a write, a dirty flag 312 in the cache control block 300 _(i) may be set to indicate the track is modified. If (at block 514) the track format code valid flag 316 is invalid, meaning there is no fast access to track format information available through the track format code 314, then the storage manager 144 returns (at block 504) fail on the bus interface to the bus host adaptor 128 because the track format table 200 cannot be used, and the track metadata needs to be read from the storage 104, which would introduce too much latency for the fast read/write on the first channel.

With the embodiment of operations of FIG. 5, during a fast write over the bus interface or first channel, if the track format metadata may be accessed without latency through the track format table 200, then the read/write request is allowed to proceed when the transaction can be processed very quickly because the track metadata can be obtained directly from the track format table 200 through the track format code 314, without having to read the track metadata from storage 104. However, if the cache control block 300 _(i) does not have a valid track format code 314 to allow low latency access of track format metadata, then the read/write request is failed because the transaction will not likely complete within a fast time threshold. This determination is important to avoid host delays in processing other tasks while the host processor is spinning on the thread handling the read/write request while waiting for the read/write request to complete. If the track metadata can be accessed from the track format table 200 than there is a high likelihood the read/write can complete on the bus interface channel within the time required to avoid the host processor holding the thread for too long, which causes other I/O requests to be queued and delayed. If the track metadata cannot be accessed from the track format table 200 and needs to be read from the storage 104, then it is unlikely the read/write request will complete within the time threshold for the host processor to spin on the thread for the read/write request, and failure is returned. Returning failure when the track metadata cannot be obtained from the track format table 200 causes the host thread waiting on the read/write request task to be deactivated and the host processor may context switch to processing other tasks, and then the read/write request is retried on the second network channel during the context switch.

Further, indication is made at block 512 that no determination was made as to whether the track format table 200 supports the new modified track format metadata, so that this determination of the track format code for the track format metadata may be made later, because supportability is unknown at this point.

FIG. 6 illustrates an embodiment of operations performed by the cache manager 142 and storage manager 144 to process a read/write request to a target track received on a second channel, such as the network 122 on network host adaptor 134. Upon receiving (at block 600) the read/write request, if (at block 602) the target track is not in the cache 140, then the cache manager 142 stages (at block 604) the track from the storage 104 to the cache 140 and reads (at block 606) the track metadata for the target track from the storage 104 to determine the track format, e.g., size of blocks, control interval, layout of records on the track, etc. If (at block 608) the read/write request is a write and if (at block 610) the write modifies the track format, then the cache manager 142 updates (at block 612) the track metadata to indicate the modified track format and sets (at block 614) the track format code valid flag 316 to invalid. The cache manager 142 indicates (at block 615) in the track format table support information 318 that no determination was made whether the track format table 200 supports the new track format metadata resulting from the write to the track modifying the track format. This indication is made to later provide information that there is still a likelihood that a track format code 202 may be supported in the track format table 200 for the new modified track format, because no such determination has been made at this point. The track metadata 312 is further updated (at block 616) to indicate the track is modified or dirty. If (at block 608) the request is a read or from block 616, the cache manager 142 uses (at block 618) the track format layout indicated in the track format metadata to process the read or write request to the target track in the cache 140.

If (at block 602) the target track is in the cache 140 and if (at block 630) the track format code valid flag 316 is set to valid, then the cache manager 142 determines (at block 632) the track format metadata 204 in the track format table 200 corresponding to the track format code 314 in the cache control block 300 _(i) for the target track. From block 632, control proceeds to block 608 to process the read/write request. If (at block 630) the track format code valid flag 316 is set to invalid, then control proceeds to block 606 to read the metadata for the track form the storage 104 to determine the track format layout.

With the embodiment of FIG. 6, when the read/write request is received on the second slower channel, such as over the network 122, where the host operating system 111 would have performed a context switch for the thread handling the read/write request, the cache manager 142 may read the track metadata from the storage 104 to determine the track layout to process the request. During this time, the host processing of further host requests is not delayed because the host thread handling the read/write request is context switched and not active, until the read/write request returns complete.

FIG. 7 illustrates an embodiment of operations performed by the cache manager 142 when closing the track metadata for a track in the cache 140, which involves destaging the track metadata to the storage 104 if changed. Upon closing (at block 700) the track metadata for a track in the cache 140, the cache manager 142 processes (at block 702) the track metadata to determine a track format or a layout of data in the track. If (at block 704) the track format table 200 does not have a track format metadata 204 matching the determined track format from the track metadata, which may happen if the determined track format is irregular, then the track format code valid flag 316 is set (at block 706) to invalid and the track format table support information 318 is set (at block 708) to indicate the track format table 200 does not include a track format code 202 for the track format metadata of the track. In such situation, read./write requests to the track having an irregular format are only processed when received through the second channel via network host adaptor 134.

If (at block 704) the track format table has a track format metadata 204 matching the determined track format from the track metadata, then the cache manager 142 determines the track format code 202 for the determined track format metadata 204 in the track format table 200 and includes the track format code 202 in the field 314 in the cache control block 300 _(i). The track format code valid flag 316 is set (at block 716) to valid and the track format table support information 318 is set (at block 718) to indicate the track format table 200 includes a track format code 202 for the track format metadata of the track. From block 708 or 718, control proceeds to block 720 to destage the track metadata from the memory 138 if modified or discard if not modified.

With the operations of FIG. 7, the track format information may be indicated in the cache control block 300 _(i) with a track format code 202 having a limited number of bits to index track format metadata 204 describing track layout in a track format table 200, where the track metadata itself would not fit into the cache control block 300 _(i). For future read/write accesses, if a valid track format code 314 is provided, then the cache manager 142 may use that code 314 to obtain with low latency the track format metadata 204 from the track format table 200 without having to read the track metadata from the storage 104 and process to determine the track format. Further, the track format table support information 318 is updated to indicate that the track format table 200 supports or does not support the track format metadata of the track. This track format table support information 318 may be subsequently used to determine whether to rebuild the track metadata for a track to determine if there is a track format code 202 for the track format metadata if the track metadata is invalidated.

FIG. 8 illustrates an embodiment of operations performed by the cache manager 142 to invalidate track format information, such as track format codes 312 saved for tracks in cache 140. Upon initiating (at block 800) an operation to invalidate a metadata track, a determination is made (at block 802) of tracks having metadata in the metadata track to invalidate. If (at block 804) the cache control block directory 300 includes cache control blocks 300 _(i) for any of the determined tracks having metadata in the metadata track to invalidate, then the track format code valid flag 316 in each of the determined cache control blocks is set (at block 806) to indicate the track format code 314 is invalid. If (at block 1204) the cache control block directory 300 does not include cache control blocks for any of the determined tracks or after setting (at block 806) the valid flag 316 to invalid, control ends. After block 806, the previously determined track format table support information 318 would be available to indicate whether it would be worthwhile to utilize processing resources to access or rebuild the track metadata to determine whether the track format table 200 includes a track format code 202 that can be used when subsequently processing requests to the track.

FIG. 9 illustrates an embodiment of the storage system 102 of FIG. 1 as including a first and second processing nodes 900 a, 900 b, which may each include a processing complex 136 and memory 138 as described with respect to FIG. 1. The first 900 a and second 900 b processing nodes each include a cache 902 a, 902 b, respectively, such as cache 140 described with respect to FIG. 1, and a non-volatile storage (“NVS”) 904 a, 904 b to backup modified tracks from the other cache 902 b, 902 a. For instance NVS 904 a would backup modified tracks in the cache 902 b in the second processing node 900 b and NVS 904 b would backup modified tracks in the cache 902 a in the first processing node 900 a. In this way, the NVSs 904 a, 904 b backup modified tracks on different power boundaries. Each processing node 900 a, 900 b further maintains a failover manager 906 a, 906 b to determine whether to failover to the other processing node 900 b, 900 a. Because each processing node 900 a, 900 b may be on a separate power boundary, the NVS 904 a, 904 b in one processing node 900 a, 900 b provides backup storage for the modified tracks in the cache 902 b, 902 a of the other processing node 900 b, 900 a to be made available in case the other processing node experiences failure or data loss/corruption.

FIG. 10 illustrates an embodiment of operations performed by the cache manager 142 and/or failover manager 906 a, 906 b to update the track format table support information 318 when performing a failover. Upon initiating (at block 1000) an operation to failover from a second processing node 900 b to a first processing node 900 a including the cache 902 a and a non-volatile storage (NVS) 904 a backing-up modified tracks in the second cache 902 b in the second processing node 900 b, the failover manager 906 a copies (at block 1002) the tracks in the first NVS 904 a, comprising modified tracks in the second cache 902 b in the second processing node 900 b, to the first cache 902 a. The cache manager 142 generates (at block 1004) a cache control block 300 _(i) for each of the tracks copied to the first cache 902 a from the first NVS 902 b and sets (at block 1006) the valid flag 316 in each of the generated cache control blocks 300 _(i) to invalid because no track format code has yet been determined for these tracks added to the cache 902 a. Indication is made (at block 1008) in the track format table support information 318 that no determination was made whether the track format metadata for the copied tracks is included in the track format table 200.

FIG. 11 illustrates an embodiment of operations performed by the cache manager 142 to determine whether to expend the effort and resources to rebuild track metadata for a track and determine whether the track format table 200 provides a track format code 202 for the track. In one embodiment, this operation to determine whether to determine a track format code may be performed in response to returning fail on the first channel, at block 504 in FIG. 5. In alternative embodiments, this operation may be performed at other stages than after returning fail on the first fast channel, e.g., bus interface 116, 118, 128. Upon initiating (at block 1100) the operation to determine the track format codes 202 for tracks having an invalid track format code, such as if the valid flag 316 indicates invalid, the cache manager 142 determines (at block 1102) whether the track format table support information 318 indicates that there may be a valid track format code 202 for the track format metadata, such as if no determination was made whether the track format table 200 includes the track format metadata for the track or that the track format table 200 previously included the track format code 202 for the track. If so, then the cache manager 142 rebuilds (at block 1104) the track metadata for the track including the track format metadata. The cache manager 142 then performs (at block 1106) the operations at blocks 702-718 in FIG. 7 to determine whether there is a track format code for the rebuilt track format metadata to include in the cache control block and to indicate track format table support information.

If (at block 1102) the track format table support information 318 indicates that the track format code 202 was not previously determined because the track format table 200 did not provide a track format code 202 for the track format metadata, then control ends without trying to determine whether the track format table 200 includes a track format code 202.

With the described embodiments, the cache manager 142 will expend the time and resources to rebuild the track metadata and try to determine a track format code 202 for the rebuilt track metadata if the track format table support information 318 indicates that there is a possibility the track format table 200 would have a code 202 for the track format metadata. If there is not a possibility, such as if a determination was made that the track format table 200 does not provide a code 202, then the cache manager 142 will not expend the resources to try to determine the track format code 202. However, if there is a possibility the track format table 200 has a code, such as if a code 202 was previously determined for the track format metadata or there was no determination made whether the track format table 200 had the code 202 when the track format code was invalidated, such as during a failover (FIG. 1), then the cache manager 142 makes the effort to determine the track format code 202 to use for later read or write operations to reduce the latency of processing subsequent read or write operations.

The present invention may be implemented as a system, a method, and/or a computer program product. The computer program product may include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present invention.

The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.

Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.

Computer readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like, and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions.

These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.

The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.

The computational components of FIG. 1, including the host 100, storage system 102, and processing nodes 900 a, 900 b may be implemented in one or more computer systems, such as the computer system 1202 shown in FIG. 12. Computer system/server 1202 may be described in the general context of computer system executable instructions, such as program modules, being executed by a computer system. Generally, program modules may include routines, programs, objects, components, logic, data structures, and so on that perform particular tasks or implement particular abstract data types. Computer system/server 1202 may be practiced in distributed cloud computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed cloud computing environment, program modules may be located in both local and remote computer system storage media including memory storage devices.

As shown in FIG. 12, the computer system/server 1202 is shown in the form of a general-purpose computing device. The components of computer system/server 1202 may include, but are not limited to, one or more processors or processing units 1204, a system memory 1206, and a bus 1208 that couples various system components including system memory 1206 to processor 1204. Bus 1208 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnects (PCI) bus.

Computer system/server 1202 typically includes a variety of computer system readable media. Such media may be any available media that is accessible by computer system/server 1202, and it includes both volatile and non-volatile media, removable and non-removable media.

System memory 1206 can include computer system readable media in the form of volatile memory, such as random access memory (RAM) 1210 and/or cache memory 1212. Computer system/server 1202 may further include other removable/non-removable, volatile/non-volatile computer system storage media. By way of example only, storage system 1213 can be provided for reading from and writing to a non-removable, non-volatile magnetic media (not shown and typically called a “hard drive”). Although not shown, a magnetic disk drive for reading from and writing to a removable, non-volatile magnetic disk (e.g., a “floppy disk”), and an optical disk drive for reading from or writing to a removable, non-volatile optical disk such as a CD-ROM, DVD-ROM or other optical media can be provided. In such instances, each can be connected to bus 1208 by one or more data media interfaces. As will be further depicted and described below, memory 1206 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the invention.

Program/utility 1214, having a set (at least one) of program modules 1216, may be stored in memory 1206 by way of example, and not limitation, as well as an operating system, one or more application programs, other program modules, and program data. Each of the operating system, one or more application programs, other program modules, and program data or some combination thereof, may include an implementation of a networking environment. The components of the computer 1202 may be implemented as program modules 1216 which generally carry out the functions and/or methodologies of embodiments of the invention as described herein. The systems of FIG. 1 may be implemented in one or more computer systems 1202, where if they are implemented in multiple computer systems 1202, then the computer systems may communicate over a network.

Computer system/server 1202 may also communicate with one or more external devices 1218 such as a keyboard, a pointing device, a display 1220, etc.; one or more devices that enable a user to interact with computer system/server 1202; and/or any devices (e.g., network card, modem, etc.) that enable computer system/server 1202 to communicate with one or more other computing devices. Such communication can occur via Input/Output (I/O) interfaces 1222. Still yet, computer system/server 1202 can communicate with one or more networks such as a local area network (LAN), a general wide area network (WAN), and/or a public network (e.g., the Internet) via network adapter 1224. As depicted, network adapter 1224 communicates with the other components of computer system/server 1202 via bus 1208. It should be understood that although not shown, other hardware and/or software components could be used in conjunction with computer system/server 1202. Examples, include, but are not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data archival storage systems, etc.

The terms “an embodiment”, “embodiment”, “embodiments”, “the embodiment”, “the embodiments”, “one or more embodiments”, “some embodiments”, and “one embodiment” mean “one or more (but not all) embodiments of the present invention(s)” unless expressly specified otherwise.

The terms “including”, “comprising”, “having” and variations thereof mean “including but not limited to”, unless expressly specified otherwise.

The enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise.

The terms “a”, “an” and “the” mean “one or more”, unless expressly specified otherwise.

Devices that are in communication with each other need not be in continuous communication with each other, unless expressly specified otherwise. In addition, devices that are in communication with each other may communicate directly or indirectly through one or more intermediaries.

A description of an embodiment with several components in communication with each other does not imply that all such components are required. On the contrary a variety of optional components are described to illustrate the wide variety of possible embodiments of the present invention.

When a single device or article is described herein, it will be readily apparent that more than one device/article (whether or not they cooperate) may be used in place of a single device/article. Similarly, where more than one device or article is described herein (whether or not they cooperate), it will be readily apparent that a single device/article may be used in place of the more than one device or article or a different number of devices/articles may be used instead of the shown number of devices or programs. The functionality and/or the features of a device may be alternatively embodied by one or more other devices which are not explicitly described as having such functionality/features. Thus, other embodiments of the present invention need not include the device itself.

The foregoing description of various embodiments of the invention has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. It is intended that the scope of the invention be limited not by this detailed description, but rather by the claims appended hereto. The above specification, examples and data provide a complete description of the manufacture and use of the composition of the invention. Since many embodiments of the invention can be made without departing from the spirit and scope of the invention, the invention resides in the claims herein after appended. 

What is claimed is:
 1. A computer program product for managing metadata for tracks in storage cached in a cache, the computer program product comprising a computer readable storage medium having computer readable program code embodied therein that is executable to perform operations, the operations comprising: maintaining a track format table providing track format codes for different track format metadata and storing the track format metadata for which the track format codes are provided; determining whether there is a possibility that the track format table has a valid track format code for track format metadata for a track; and rebuilding track format metadata for the track in response to determining that there is a possibility the track format table has a track format code for the track format metadata for the track.
 2. The computer program product of claim 1, wherein the track format metadata is not rebuilt in response to determining that there is no possibility the track format table has the valid track format code for the track.
 3. The computer program product of claim 1, wherein the determining whether there is the possibility the track format table has the valid track format code comprises determining at least one of: that no determination was made whether the track format table includes track format metadata for the track; and that the track format table includes the track format code for the track.
 4. The computer program product of claim 1, wherein the determining whether there is the possibility that the track format table has the valid track format code for track format metadata for the track and rebuilding the track format metadata for the track are performed in response to a request to access track format metadata for the track when the request to access the track failed on a first channel and was retried on a second channel.
 5. The computer program product of claim 1, wherein the operations further comprise: determining whether the track format table has a track format matching the rebuilt track format metadata; determining a track format code in the track format table for the track format matching the rebuilt track format metadata; including the determined track format code in a cache control block for the track; and indicating that there is a possibility that the track format table includes the track format code for the track in response to determining the track format code.
 6. The computer program product of claim 1, wherein the operations further comprise: determining whether the track format table has a track format matching the rebuilt track format metadata; determining a track format code in the track format table for the track format matching the rebuilt track format metadata; and indicating that the track format table does not include the track format code for the track format metadata for the track in response to determining that the track format table does not have a track format matching the rebuilt track format metadata.
 7. The computer program product of claim 1, wherein a cache control block for the track indicates whether there is a possibility that a track format table has a valid track format code for track format metadata for the track.
 8. A system for managing metadata for tracks in a storage, comprising: a processor; a cache; and a computer readable storage medium having computer readable program code embodied therein that when executed by the processor performs operations, the operations comprising: maintaining a track format table providing track format codes for different track format metadata and storing the track format metadata for which the track format codes are provided; determining whether there is a possibility that the track format table has a valid track format code for track format metadata for a track; and rebuilding track format metadata for the track in response to determining that there is a possibility the track format table has a track format code for the track format metadata for the track.
 9. The system of claim 8, wherein the track format metadata is not rebuilt in response to determining that there is no possibility the track format table has the valid track format code for the track.
 10. The system of claim 8, wherein the determining whether there is the possibility the track format table has the valid track format code comprises determining at least one of: that no determination was made whether the track format table includes track format metadata for the track; and that the track format table includes the track format code for the track.
 11. The system of claim 8, wherein the determining whether there is the possibility that the track format table has the valid track format code for track format metadata for the track and rebuilding the track format metadata for the track are performed in response to a request to access track format metadata for the track when the request to access the track failed on a first channel and was retried on a second channel.
 12. The system of claim 8, wherein the operations further comprise: determining whether the track format table has a track format matching the rebuilt track format metadata; determining a track format code in the track format table for the track format matching the rebuilt track format metadata; including the determined track format code in a cache control block for the track; and indicating that there is a possibility that the track format table includes the track format code for the track in response to determining the track format code.
 13. The system of claim 8, wherein the operations further comprise: determining whether the track format table has a track format matching the rebuilt track format metadata; determining a track format code in the track format table for the track format matching the rebuilt track format metadata; and indicating that the track format table does not include the track format code for the track format metadata for the track in response to determining that the track format table does not have a track format matching the rebuilt track format metadata.
 14. The system of claim 8, wherein a cache control block for the track indicates whether there is a possibility that a track format table has a valid track format code for track format metadata for the track.
 15. A method for managing metadata for tracks in a storage cached in a cache, comprising: maintaining a track format table providing track format codes for different track format metadata and storing the track format metadata for which the track format codes are provided; determining whether there is a possibility that the track format table has a valid track format code for track format metadata for a track; and rebuilding track format metadata for the track in response to determining that there is a possibility the track format table has a track format code for the track format metadata for the track.
 16. The method of claim 15, wherein the track format metadata is not rebuilt in response to determining that there is no possibility the track format table has the valid track format code for the track.
 17. The method of claim 15, wherein the determining whether there is the possibility the track format table has the valid track format code comprises determining at least one of: that no determination was made whether the track format table includes track format metadata for the track; and that the track format table includes the track format code for the track.
 18. The method of claim 15, further comprising: determining whether the track format table has a track format matching the rebuilt track format metadata; determining a track format code in the track format table for the track format matching the rebuilt track format metadata; including the determined track format code in a cache control block for the track; and indicating that there is a possibility that the track format table includes the track format code for the track in response to determining the track format code.
 19. The method of claim 15, further comprising: determining whether the track format table has a track format matching the rebuilt track format metadata; determining a track format code in the track format table for the track format matching the rebuilt track format metadata; and indicating that the track format table does not include the track format code for the track format metadata for the track in response to determining that the track format table does not have a track format matching the rebuilt track format metadata.
 20. The method of claim 15, wherein a cache control block for the track indicates whether there is a possibility that a track format table has a valid track format code for track format metadata for the track. 